feat: add support for nitro v3 #8

schplitt · 2026-01-27T10:25:22Z

🔗 Linked issue

resolves #7

📚 Description

This PR adds support for early nitro v3 alpha versions under the evlog/nitrov3 scope.
Hope that is alright.

I move shared nitro utilities to a seperate file.
I have adjusted the docs aswell to add a note and a playground.
Nitrov3 currently seems to have issues with runtime config support in monorepos but it should work correctly in a new project.
I am not very familiar with bun so I couldn't get the imports from the node_modules to work and used a relative path instead.
For that reason also please check if I integrated it correctly into the build config.

Please see if you would like to have anything changed!

📝 Checklist

I have linked an issue or discussion.
I have updated the documentation accordingly.

vercel · 2026-01-27T10:25:27Z

@schplitt is attempting to deploy a commit to the HRCD Projects Team on Vercel.

A member of the Team first needs to authorize it.

github-actions · 2026-01-27T10:25:35Z

Thank you for following the naming conventions! 🙏

HugoRCD · 2026-01-27T10:50:15Z

@schplitt I don't know if it's better, but I'd prefer to have an entry point that looks more like 'evlog/nitro/v3'. I don't really like having nitrov3 attached and it will be easier to migrate later by just removing /v3 and maybe replace v3 with v2 for migration 🤔. Otherwise, we'd also need a more 'complete' playground and tests as well! (If you don't have time, I can take care of it later)

schplitt · 2026-01-27T10:52:22Z

@schplitt I don't know if it's better, but I'd prefer to have an entry point that looks more like 'evlog/nitro/v3'. I don't really like having nitrov3 attached and it will be easier to migrate later by just removing /v3 and maybe replace v3 with v2 for migration 🤔. Otherwise, we'd also need a more 'complete' playground and tests as well! (If you don't have time, I can take care of it later)

Should the 'complete' playground be like v2 or even more extensive?

HugoRCD · 2026-01-27T10:55:32Z

@schplitt I don't know if it's better, but I'd prefer to have an entry point that looks more like 'evlog/nitro/v3'. I don't really like having nitrov3 attached and it will be easier to migrate later by just removing /v3 and maybe replace v3 with v2 for migration 🤔. Otherwise, we'd also need a more 'complete' playground and tests as well! (If you don't have time, I can take care of it later)

Should the 'complete' playground be like v2 or even more extensive?

Ideally similar, but otherwise just a little less comprehensive is fine with me too. It's just so we can easily launch the app and quickly test that everything works without having to do too much setup.

schplitt · 2026-01-27T10:56:41Z

Alright
I'll take care of that

schplitt · 2026-01-27T12:38:35Z

Improved the playground to serve a basic UI to visualize the error aswell

Also moved nitrov3 to nitro/v3 in dist 🙂

schplitt · 2026-01-27T13:30:18Z

I noticed that in v3 the error is transformed into an unhandled HTTPError before we have access to it
So this isn't actually working yet.

We would need to overwrite the entire error handler to be able to handle EvlogErrors correctly
Or have EvlogErrors extend HTTPErrors in nitro v3

HugoRCD · 2026-01-27T18:45:34Z

I noticed that in v3 the error is transformed into an unhandled HTTPError before we have access to it So this isn't actually working yet.

We would need to overwrite the entire error handler to be able to handle EvlogErrors correctly Or have EvlogErrors extend HTTPErrors in nitro v3

I'll try to see how we can do that too

pkg-pr-new · 2026-01-27T18:57:03Z

npm i https://pkg.pr.new/evlog@8

commit: cd2f9fb

vercel · 2026-01-27T18:58:18Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
evlog-docs	Ready	Preview, Comment	Jan 31, 2026 1:35pm

HugoRCD · 2026-01-27T22:10:03Z

I just realized that I'm not even sure if this is supposed to work, or if it will ever work 😅

schplitt · 2026-01-28T09:39:31Z

I just realized that I'm not even sure if this is supposed to work, or if it will ever work 😅

What exactly are you referring to?

HugoRCD · 2026-01-28T09:42:22Z

I just realized that I'm not even sure if this is supposed to work, or if it will ever work 😅

What exactly are you referring to?

I don't know if this syntax, where you put a plugin (imported from npm) directly into the plugin array, works. The documentation doesn't mention it

schplitt · 2026-01-28T09:58:44Z

I am not sure what the future plans for nuxt and evlog are but as nitro will become framework agnostic and interop with vite plugins, maybe it would be a nice Idea to experiment with nitro modules:
nitrojs/nitro#3680

So that it could also be used with tanstack, etc.?
Though just an idea.

Let me know what your plans are going forward regarding nitro v3 and I'll see how I can help🙂

HugoRCD · 2026-01-28T10:27:11Z

@schplitt Oh, nice! So I think we should implement it like that, and clean up the repo to have a Nitro v2 playground and a Nitro v3 (update the PR with the latest features I added)

schplitt · 2026-01-28T16:27:11Z

I noticed that in v3 the error is transformed into an unhandled HTTPError before we have access to it So this isn't actually working yet.
We would need to overwrite the entire error handler to be able to handle EvlogErrors correctly Or have EvlogErrors extend HTTPErrors in nitro v3

I'll try to see how we can do that too

What about your preferred solution for this?

HugoRCD · 2026-01-28T16:30:15Z

I noticed that in v3 the error is transformed into an unhandled HTTPError before we have access to it So this isn't actually working yet.
We would need to overwrite the entire error handler to be able to handle EvlogErrors correctly Or have EvlogErrors extend HTTPErrors in nitro v3

I'll try to see how we can do that too

What about your preferred solution for this?

So I would lean towards "simplicity" and extend HTTPError

schplitt · 2026-01-28T17:38:52Z

I've looked into this a bit.
I think there is not really an "easy" way to do this.

First, we would make Evlog dependend on H3 v2 HTTPError which I think is incompatible with Nuxt and Nitro v2.

Second, the HTTPError interface is a bit different then what is currently expeced (e.g. extra body property for the returned response). It may be best to create another utility for Nitro v3 and export it from there to not have Nitro v2 and Nuxt be dependend on H3 v2.

schplitt · 2026-01-31T17:16:49Z

So I've finally had time to fix up the nitro/v3 functionality.

Now it uses H3's HTTPError. Though there are still a couple of issues that need to be resolved:

Runtime Config Bundling Issue

When the plugin for Nitro v3 is bundled, it also bundles the reference to useRuntimeConfig() which results in it not actually having access to the correct runtime config but a mock. It also causes this warning in the terminal:

WARN  Nitro runtime imports detected without a builder or Nitro plugin. A stub implementation will be used.

TBH I have not yet found a better solution than actually copying the file into the package and having nitro transpile it at run/build time. But the necessary imports from evlog would need to be available from the package itself, though that seems to be possible. This would mean some logic cannot be shared (e.g., the shouldLog function).

Actually I think we can just mark nitro/runtime-config as external. This way the import is resolved by nitro at run/buildtime.

Error Name Display

When the Error is logged, it still says HTTPError in the log message as we cannot overwrite the name of HTTPError:

16:42:33.410 ERROR [app] PUT /api/test/update 403 in 261ms
  ├─ requestId: b191342e-c394-4d2e-a5b3-b35df0574bb2
  ├─ user: id=999
  ├─ action: update_item
  ├─ item: name=My Item version=2.0
  ├─ validation: checked=true
  ├─ permissions: checked=true hasUpdate=false requiredRole=admin
  └─ error: name=HTTPError message=Update failed stack=HTTPError: Update failed
    at createError (file:///home/schplitt/vsc/evlog/packages/evlog/dist/nitro/v3/plugin.mjs:56:10)
    at file:///home/schplitt/vsc/evlog/apps/nitro-v3-playground/node_modules/.nitro/dev/index.mjs:819:9

Note: In Nitro v3, every Error besides HTTPError is automatically marked as unhandled which causes an even bigger error log

EvlogError: Update failed
    at createError (file:///home/schplitt/vsc/evlog/packages/evlog/dist/nitro/v3/plugin.mjs:59:10)
    at file:///home/schplitt/vsc/evlog/apps/nitro-v3-playground/node_modules/.nitro/dev/index.mjs:819:9 {
  cause: EvlogError: Update failed
      at createError (file:///home/schplitt/vsc/evlog/packages/evlog/dist/nitro/v3/plugin.mjs:59:10)
      at file:///home/schplitt/vsc/evlog/apps/nitro-v3-playground/node_modules/.nitro/dev/index.mjs:819:9 {
    cause: {
      cause: undefined,
      body: [Object],
      statusCode: 403,
      unhandled: false
    },
    status: 403,
    statusText: undefined,
    headers: undefined,
    data: undefined,
    body: {
      why: 'Insufficient permissions to update this resource',
      fix: 'Request admin privileges or contact your team lead',
      link: 'https://docs.example.com/permissions'
    },
    unhandled: false,
    why: 'Insufficient permissions to update this resource',
    fix: 'Request admin privileges or contact your team lead',
    link: 'https://docs.example.com/permissions'
  },
  status: 403,
  statusText: undefined,
  headers: undefined,
  data: undefined,
  body: {
    why: 'Insufficient permissions to update this resource',
    fix: 'Request admin privileges or contact your team lead',
    link: 'https://docs.example.com/permissions'
  },
  unhandled: true
}
16:39:56.331 ERROR [app] PUT /api/test/update 403 in 261ms
  ├─ requestId: 5bac1ec9-c6d6-47f2-9d56-da1b3a48e82c
  ├─ user: id=999
  ├─ action: update_item
  ├─ item: name=My Item version=2.0
  ├─ validation: checked=true
  ├─ permissions: checked=true hasUpdate=false requiredRole=admin
  └─ error: name=HTTPError message=Update failed stack=EvlogError: Update failed
    at createError (file:///home/schplitt/vsc/evlog/packages/evlog/dist/nitro/v3/plugin.mjs:59:10)
    at file:///home/schplitt/vsc/evlog/apps/nitro-v3-playground/node_modules/.nitro/dev/index.mjs:819:9

 ERROR  [request error] [unhandled] [PUT] http://localhost:3000/api/test/update

 
ℹ HTTPError: Update failed

 ⁃ at createError (/home/schplitt/vsc/evlog/packages/evlog/dist/nitro/v3/plugin.mjs:59:10)

   54 ┃      }
   55 ┃      return lines.join("\n");
   56 ┃    }
   57 ┃  }
   58 ┃  function createError(options) {
 ❯ 59 ┃    return new EvlogError(options);
   60 ┃  }
   61 ┃  const createEvlogError = createError;
   62 ┃  
   63 ┃  const plugin = definePlugin((nitroApp) => {
   64 ┃    const config = useRuntimeConfig();

 ⁃ (node_modules/.nitro/dev/index.mjs:819:9)

[CAUSE]
EvlogError {
  stack: 'Update failed\n' +
  'at createError (/home/schplitt/vsc/evlog/packages/evlog/dist/nitro/v3/plugin.mjs:59:10)\n' +
  'at ./node_modules/.nitro/dev/index.mjs:819:9)',
  message: 'Update failed',
  cause: {
    cause: undefined,
    body: [Object],
    statusCode: 403,
    unhandled: false,
  },
  status: 403,
  statusText: undefined,
  headers: undefined,
  data: undefined,
  body: {
    why: 'Insufficient permissions to update this resource',
    fix: 'Request admin privileges or contact your team lead',
    link: 'https://docs.example.com/permissions',
  },
  unhandled: false,
  why: 'Insufficient permissions to update this resource',
  fix: 'Request admin privileges or contact your team lead',
  link: 'https://docs.example.com/permissions',
}

It may be a bit confusing why the error from createError shows as HTTPError in the logs.

Missing body

Currently Nitro v3 doesn't correctly pass the body back to the user (why, link, ...). But this is already being fixed.

Any wishes on how to best go forward with this @HugoRCD ?

schplitt · 2026-02-08T21:30:26Z

@HugoRCD Just following up on this PR. I'm actively using Nitro v3 and would love to land this early support.

The issues from my last comment should all be easy to address:

Solvable by marking runtime-config as external
& 3. Can be handled via a custom error handler (same approach as Nitro v2)

I'm ready to bring this up to feature parity and merge it, but happy to wait for a more stable Nitro v3 release and keep the integration in my own project for now if you prefer.

Just let me know which direction works for you. I'd like to move forward when you have a moment.

HugoRCD · 2026-02-10T09:13:47Z

I don't know, I really want to have Nitro v3 support as soon as possible, but at the same time, I'm not sure if it's reasonable to wait for a more stable version? 🤔

schplitt · 2026-02-10T12:17:59Z

Early support would be much appreciated.
As mainly existing features from Nitrov2 are used (plugins, error handler) I doubt there will be many breaking changes.

If you are worried about maintance, I am willing to help out as much as I can for keeping the v3 version up to date. 🙂

HugoRCD · 2026-02-10T12:19:53Z

Early support would be much appreciated.

As mainly existing features from Nitrov2 are used (plugins, error handler) I doubt there will be many breaking changes.

If you are worried about maintance, I am willing to help out as much as I can for keeping the v3 version up to date. 🙂

Nice, so let's go and make this happen !

schplitt · 2026-02-10T20:15:41Z

@HugoRCD Brought it up to speed.
We can now just use the plain evlog createError function in nitro v3 aswell with the custom error handler.

Test with nitro v3 use a real development server.
To check if the actual runtime hooks are working is by logging them and catching the logs using consola.
For this to work correctly we run them sequentially and check the logs.
Was the easiest and cleanest solution I could think of right now, hope that's alright.
I also cleaned up the playground.

If anything like tests or features are missing, just tell me and I'll add them aswell.
You did so much here so could very well be I overlooked something ❤️

HugoRCD · 2026-02-10T20:17:30Z

@HugoRCD Brought it up to speed. We can now just use the plain evlog createError function in nitro v3 aswell with the custom error handler.

Test with nitro v3 use a real development server. To check if the actual runtime hooks are working is by logging them and catching the logs using consola. For this to work correctly we run them sequentially and check the logs. Was the easiest and cleanest solution I could think of right now, hope that's alright. I also cleaned up the playground.

If anything like tests or features are missing, just tell me and I'll add them aswell. You did so much here so could very well be I overlooked something ❤️

Ty 🙏 I'll take a look at that!

HugoRCD · 2026-02-10T20:23:04Z

apps/nitro-v3-playground/nitro.config.ts

+export default defineConfig({
+  serverDir: './',
+  // TODO: make playground work with evlog/nitro/v3
+  plugins: ['../../packages/evlog/src/nitro-v3/plugin.ts'],


Weren't we supposed to run the system by just putting evlog/nitro/v3 here?

Same as the other issue, bun workspaces does not seem to resolve the dependency correctly and thus does not install it into the node_modules dir.
Does it work for you?

apps/nitro-v3-playground/README.md

HugoRCD · 2026-02-10T20:26:31Z

apps/nitro-v3-playground/tsconfig.json

+      "~/*": ["./*"],
+      "evlog": ["../../packages/evlog/src/index.ts"],
+      "evlog/*": ["../../packages/evlog/src/*"]
+    }


Do we really need to customize tsconfig? Ideally, I would like the user to have as little to configure as possible

Bun workspaces does not resolve the types correctly.
It doesn't seem to correctly install the evlog package from the workspace on my machine

HugoRCD · 2026-02-10T20:28:51Z

packages/evlog/package.json

+    "@nuxt/kit": "^4.3.0",
+    "ufo": "^1.6.3"
+  },
  "devDependencies": {


I made sure that the lib is no longer a dependency. Do you think you can remove that?

I'll take a look how to minimize it/extract the logic to a local function.
Would inlining also be an option?

schplitt added 7 commits January 27, 2026 11:15

feat: add nitrov3 support

85f1c22

chore: add ufo package to dependencies

3fc91f7

docs: add note for early Nitro v3 support in installation guide

d55f967

chore: initialize nitrov3 playground

e25ae9b

revert: nitro 2 playground

e6e9445

chore: add nitrov3 output to package.json

9d005f0

docs: add note for early Nitro v3 support in README

0b1592a

github-actions bot added the feature label Jan 27, 2026

schplitt added 3 commits January 27, 2026 13:32

chore: better nitro v3 playground

6e7727d

chore: expose nitro v3 at nitro/v3

ef07be7

chore: update Nitro v3 references to use evlog/nitro/v3

6171d49

Merge branch 'main' into feat/nitrov3-support

d307849

HugoRCD changed the title ~~feat: add support for nitrov3~~ feat: add support for nitro v3 Jan 27, 2026

up

0994c10

vercel bot deployed to Preview January 27, 2026 18:59 View deployment

schplitt closed this Jan 28, 2026

schplitt reopened this Jan 28, 2026

schplitt added 3 commits January 31, 2026 13:56

feat(nitro-v3): align EvlogError with Nitro v3 HTTPError contract

90e2c45

Merge remote-tracking branch 'origin/main' into feat/nitrov3-support

f6e7b73

nitro/v3 feature parity

23c32cd

vercel bot deployed to Preview January 31, 2026 13:35 View deployment

schplitt added 3 commits January 31, 2026 17:43

fix: error handling/logging

2bd17f6

Merge remote-tracking branch 'origin/main' into feat/nitrov3-support

860568f

nitrov3 respect exclude config

4d7b5e4

schplitt added 7 commits February 10, 2026 17:43

Merge remote-tracking branch 'origin/main' into feat/nitrov3-support

9dbe202

feat: nitro v3 feature parity

3fe2419

chore: deps

5e2e51d

build: add nitro v3 plugin and error handler entries to tsdown config

da5ff3a

test: nitro v3 tests

3be516a

chore: clean up nitro v3 playground

83ecf18

docs: update nitro v3 usage

cd2f9fb

schplitt mentioned this pull request Feb 10, 2026

Add logging utilities schplitt/c8y-nitro#26

Open

HugoRCD requested changes Feb 10, 2026

View reviewed changes

docs: update README for Nitro v3 playground

8b1339f

Uh oh!

feat: add support for nitro v3 #8

Are you sure you want to change the base?

feat: add support for nitro v3 #8

Conversation

schplitt commented Jan 27, 2026

🔗 Linked issue

📚 Description

📝 Checklist

Uh oh!

vercel bot commented Jan 27, 2026

Uh oh!

github-actions bot commented Jan 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

HugoRCD commented Jan 27, 2026

Uh oh!

schplitt commented Jan 27, 2026

Uh oh!

HugoRCD commented Jan 27, 2026

Uh oh!

schplitt commented Jan 27, 2026

Uh oh!

schplitt commented Jan 27, 2026

Uh oh!

schplitt commented Jan 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

HugoRCD commented Jan 27, 2026

Uh oh!

pkg-pr-new bot commented Jan 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

vercel bot commented Jan 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

HugoRCD commented Jan 27, 2026

Uh oh!

schplitt commented Jan 28, 2026

Uh oh!

HugoRCD commented Jan 28, 2026

Uh oh!

schplitt commented Jan 28, 2026

Uh oh!

HugoRCD commented Jan 28, 2026

Uh oh!

schplitt commented Jan 28, 2026

Uh oh!

HugoRCD commented Jan 28, 2026

Uh oh!

schplitt commented Jan 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

schplitt commented Jan 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

schplitt commented Feb 8, 2026

Uh oh!

HugoRCD commented Feb 10, 2026

Uh oh!

schplitt commented Feb 10, 2026

Uh oh!

HugoRCD commented Feb 10, 2026

Uh oh!

schplitt commented Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

HugoRCD commented Feb 10, 2026

Uh oh!

HugoRCD Feb 10, 2026

Choose a reason for hiding this comment

Uh oh!

schplitt Feb 10, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

HugoRCD Feb 10, 2026

Choose a reason for hiding this comment

Uh oh!

schplitt Feb 10, 2026

github-actions bot commented Jan 27, 2026 •

edited

Loading

schplitt commented Jan 27, 2026 •

edited

Loading

pkg-pr-new bot commented Jan 27, 2026 •

edited

Loading

vercel bot commented Jan 27, 2026 •

edited

Loading

schplitt commented Jan 28, 2026 •

edited

Loading

schplitt commented Jan 31, 2026 •

edited

Loading

schplitt commented Feb 10, 2026 •

edited

Loading